docs: CRM status changes and detection configs#88
Open
NikitaVr wants to merge 1 commit into
Open
Conversation
… and detection configs"
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Knowledge Update: CRM status changes and detection configs
This PR was automatically generated from a knowledge base update.
Changes
concepts/detections.mdx): Added clarification about which CRM status changes automatically affect threat detection configurationsKnowledge Entry
Topic: CRM status changes and detection configs
Added by: maksym@chainpatrol.io
Date: 2026-05-26
Content:
Original Message
Auto-generated by the ChainPatrol Knowledge Agent
Note
Low Risk
Documentation-only change with no runtime, security, or data-handling impact.
Overview
Adds a Configuration section to the detections concept doc explaining how detection sources are set up and which CRM-driven updates apply automatically.
The new Info callout states that only organization priority changes in the CRM auto-adjust threat detection configs; other CRM updates (e.g. Active → Trial) do not change detection settings or other org configuration. It also directs readers to ChainPatrol for custom detection changes.
Fixes a minor formatting issue in Key Takeaways (deduplication bullet indentation).
Reviewed by Cursor Bugbot for commit b31b16d. Bugbot is set up for automated code reviews on this repo. Configure here.